Skip to content

Conversation

tclh123
Copy link
Owner

@tclh123 tclh123 commented Nov 24, 2013

No description provided.

gotmax23 and others added 29 commits February 28, 2024 20:27
It would be great to have ppc64le manylinux wheels available on PyPI.
The change from wimglenn@aab211a incorrectly made setuptools a runtime dependency of pygit2. It is not a runtime dependency, it is only a build dependency (pkg_resources / setuptools are not used outside of the installer script setup.py). It should be possible to use pygit2 without needing setuptools installed.
On EPEL8 builds for s390x this transfers ~3040 bytes:

__________________________________ test_fetch __________________________________
emptyrepo = pygit2.Repository('/tmp/pytest-of-mockbuild/pytest-0/test_fetch0/emptyrepo/.git/')
    def test_fetch(emptyrepo):
        remote = emptyrepo.remotes[0]
        stats = remote.fetch()
        assert stats.received_bytes > 2700
>       assert stats.received_bytes < 2800
E       assert 3041 < 2800
E        +  where 3041 = <pygit2.remotes.TransferProgress object at 0x3ffa8668dd0>.received_bytes
test/test_remote.py:218: AssertionError

Would be too easy if this were deterministic.

Signed-off-by: Nils Philippsen <[email protected]>
Also use git_strarray_dispose instead of deprecated git_strarray_free.
And fix a couple of build warnings in git_commit_create.
To emphasize that the StrArray() context manager returns a pointer,
implement its ptr() property and use it whenever calling a C function
that takes a pointer to a git_strarray structure as a parameter.
Enable the StrArray() context manager to be used for assigning a list of
strings to a pre-existing git_strarray structure.  This is useful when
some other structure contains a git_strarray (rather than a pointer to
it).
Add a new keyword argument to Remote.push() that is a counterpart of
`git push --push-option=<string>`.

Fixes #1126
And small coding improvements related to git_strarray
ambv and others added 30 commits August 11, 2025 13:39
Free-threaded builds are exempt from abi3 builds
Only for GitHub actions in CI workflows.

Managing Python dependencies in this project seems to be manual driven.
It can be enabled (un-commented) later, if desired.
I just didn't want to cause PR spam.

To reduce perceivable spam, I set the "auto-check for updates" schedule to monthly.
Note, dependabot will automatically close or update any outdated PRs that it opened.
Bumps the actions group with 2 updates: [actions/checkout](https://github.com/actions/checkout) and [actions/download-artifact](https://github.com/actions/download-artifact).


Updates `actions/checkout` from 4 to 5
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v4...v5)

Updates `actions/download-artifact` from 4 to 5
- [Release notes](https://github.com/actions/download-artifact/releases)
- [Commits](actions/download-artifact@v4...v5)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: '5'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: actions
- dependency-name: actions/download-artifact
  dependency-version: '5'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: actions
...

Signed-off-by: dependabot[bot] <[email protected]>
Should avoid maintaining appveyor workflow (and free up appveyor account limitations 😉).

This also introduces windows aarch64 distributions 🎉

Lastly, I updated other spots in the GH actions workflow:

- upgrade `actions/checkout` to v5 (only breaking changes are internal like upgrade node version used for building their dist)
- turn off credential persistence in `actions/checkout` action (only useful if the workflow uses `git push` or similar)
- upgrade `actions/download-artifact` to v5 (only breaking changes are internal because this already uses `merge-multiple: true`)
- add job to check built distributions for non-tagged commits to default branch. This is meant to highlight any problems with dists' metadata before tagging a release.
- add job to build sdist (for sake of completeness)
- update README.md badges
…jects

Fixes #1381

Fear not: I have ensured that all previous entries remain as they were (just in different order with contextual comments)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.